VTG VM ERROR Alarm

• The voice mail prompt files are not installed properly, or the voice mail application is unable to communicate with MiVoice Business call control.

• Voice mail files (Master.dat, voxdrv.cfg, or vtp.vap, vte.vap, vtn.vap for any of 21 language prompts) are missing or corrupted.

• Voice mail fails to start.

• Daily audit fails due to a busy port, an active visual voice mail session, or when an audit fails twice consecutively.

• Disk usage above warning or critical threshold.

For missing voice mail files:

1. For all platforms except Container-based MiVoice Business (cMiVB), collect SOS report from Server Manager (Administration > View log files). For Container-based MiVoice Business (cMiVB), collect the log files from System Diagnostics Reporting form.

2. Check for the missing files in the diag.dat file in the SOS report.

3. Start MSPLog viewer to check msplog_xxxx.xlog for impacts on voice mail operation.

4. If the missing files are related to voice mail database, then copy the missing files from a previous valid database backup file.

5. If the missing files are related to voice mail system, such as prompt and languages, then copy the missing files from the current MiVoice Business software or re-install the software.

6. If the issue persists, contact Mitel Product Support  with MSPlogs and diag.dat files.

For daily audit failures:

1. Verify whether the port status in both mcdDebug shell and call control are idle:
• mcdDebug
  -vmPostStatusInfo
• Call control
  State 1 4 27 (Ports 1-16)
  State 1 4 28 (Ports 17-30)

The port status between mcdDebug shell and call control should match.

2. Check whether the ports are busy. For example, for port 16, run the RESOURCE 1 4 27 15 1 maintenance command. If the two ports are busy communicating with each other, force busy and Request to Service (RTS) a port.

3. If the ports are idle, then stop and start voice mail or restart the MiVoice Business system by running the RESTART maintenance command.